Blog: Cloud, Edge, or Both? How to Choose Your Deployment Before an Outage Does It For You#4921
Merged
PabloFilomeno83 merged 8 commits intomainfrom Apr 24, 2026
Merged
Conversation
…utage Does It For You
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 67.7%, saving 785.2 KB.
|
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…utage Does It For You
…utage Does It For You
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 70.3%, saving 3.6 MB.
2 images did not require optimisation. |
andreguerra7
approved these changes
Apr 24, 2026
Contributor
andreguerra7
left a comment
andreguerra7
left a comment
There was a problem hiding this comment.
@sumitshinde-84 Approved, added a few comments please check the Four questions that determine your architecture bit
| description: Talk to our team. We'll help you map the right architecture for your infrastructure, workflows, and operational constraints. | ||
| --- | ||
|
|
||
| A production line at a mid-size manufacturer goes dark for 22 minutes. Not because the machines failed. Because the WAN link between the factory and the cloud dropped. The logic controlling the line was hosted in the cloud. Without a connection, it couldn't execute. By the time the link recovered, the shift had lost a batch. |
|
|
||
| **Where it breaks:** | ||
|
|
||
| Cloud instances require a persistent connection to execute. If your workflows control or monitor equipment on a factory floor, that link becomes a single point of failure. A 30-second outage doesn't slow things down. It stops execution entirely. That's not recoverable by restarting a service. |
Contributor
There was a problem hiding this comment.
@sumitshinde-84 consider: A 30-second outage doesn't just slow things down. It can stop workflows that depend on that connection entirely.
|
|
||
| Ownership is the failure mode, not complexity. When nobody has explicitly decided who is responsible for each layer, edge and cloud configurations drift apart. One team updates a cloud flow without knowing the Remote Instance depends on it. An incident happens and two people are debugging two environments, each assuming the other owns the problem. The architecture is sound. The gap is organizational, not technical. | ||
|
|
||
| ## Four questions that determine your architecture |
Contributor
There was a problem hiding this comment.
@sumitshinde-84 Title says 4 questions but there are 5 on the image and question 2 is not mentioned on the text
PabloFilomeno83
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Related Issue(s)
Checklist